Software Language Engineering of Architectural Viewpoints
نویسندگان
چکیده
A common practice in software architecture design is to apply architectural views to design software architecture for the various stakeholder concerns. Architectural views are usually developed based on architectural viewpoints which define the conventions for constructing, interpreting and analyzing views. So far most architectural viewpoints seem to have been primarily used either to support the communication among stakeholders, or at the best to provide a blueprint for the detailed design. In this paper we provide a software language engineering approach to define viewpoints as domain specific languages. This enhances the formal precision of architectural viewpoints and leads to executable views that can be interpreted and analyzed by tools. We illustrate our approach for defining domain specific languages for the viewpoints of the Views and Beyond approach.
منابع مشابه
Identifying Architectural Viewpoints - A Scenario-Based Approach
For reverse-engineering software architectures, architectural viewpoints need to be defined in a way where all customer needs are considered. This paper presents a systematic, scenario-based approach for identifying customer-specific viewpoints. The approach was successfully applied in the Cobus II project to identify 11 customer-specific viewpoints for describing the architecture of a COBOL sy...
متن کاملUML (Unified Modeling Language): Standard Language for Software Architecture Development
A solid architectural vision is a key discriminator in the success or failure of a software project. This paper discusses how to describe architecture through a set of design viewpoints and how to express these views in the UML. In this paper we mainly focused on the standardization of UML for software development process with the discussion of benefits of UML. Object-oriented analysis (OOA) is...
متن کاملImproving the IEEE std 1471-2000 for communication among stakeholders and early design decisions
There are, at least, three reasons why software architecture is important: a) communication among stakeholders, b) early design decisions, and c) transferable abstraction of a system. The IEEE Recommended Practice for Architectural Description of Software-Intensive Systems introduces and integrates stakeholders, concerns, viewpoints, views, and architectural models facilitating the expression, ...
متن کاملKumbangSec: An Approach for Modelling Functional and Security Variability in Software Architectures
Software products often need to vary in terms of functionality, but also in terms of quality attributes. We describe KumbangSec, which in an approach for modelling functional and security variability applying different architectural viewpoints. KumbangSec builds on an existing variability modelling method, Kumbang, by extending it with security engineering concepts. KumbangSec consists of a con...
متن کاملSoftware Architectural Design Ontology
Software Architecture plays a key role in software development but absence of formal description of Software Architecture causes different impede in software development. To cope with these difficulties, ontology has been used as artifact. This paper proposes ontology for Software Architectural design based on IEEE model for architecture description and Kruchten 4+1 model for viewpoints classif...
متن کامل